The clear definition of the test products to be delivered.

Method of operation

The activities that are carried out for the purposes of planning, execution and managing the test process deliver certain products, such as the test plan and reports, test cases and test scripts, but also procedures, instructions and project documentation, such as consultation notes. In consultation with the client and other stakeholders, it is determined what products are to be delivered. If there is a master test plan, this will also define test products to be delivered. This may concern testware, such as test plans, test scripts or automated regression tests – products, therefore, that are eligible for reuse, but which also may define test documentation, such as progress reports.

• 1. Testware - In retests or regression testing, existing testware is often used. Testware covers, for example:
  
  • Test plan(s) - Include both master test plans and other test plans
  • Logical test specifications - The logical specifications contain the logical description of the test cases
  • Physical test specifications - The physical test specifications contain the physical description of the test cases and the test scripts. Physical means that the test cases are executable and checkable. The physical test cases are converted from the logical test cases. A test script contains the physical test cases placed in the most efficient order of execution.
  • Traceability matrix (or cross-reference matrix) - A matrix in which the link is indicated between the test basis (requirements, functional specifications, etc.) and the actual test cases. The situations to be tested from the test basis are shown vertically and the test cases horizontally.
  • Test input files - The test input files created on the basis of the test scripts should contain a (brief) description of the following:
    • Aim
    • The “physical” name
    • Date created
    • Brief description of the content
    • The file type and other relevant features
    • Reference to the test scripts.
  • Basic documentation - A description of the test environment, test tools, test organisation and underlying databases
  • Test execution dossier - The test execution dossier consists of:
    • Test results (logging of executed tests and test cases) and reports
    • Test execution (optional) - The “material evidence” of the executed tests can consist of screen dumps, print output and output files. After completion of the test, the tester delivers the produced output to the administrator. The test documentation to be delivered from the output contains:
      • Reference to the “physical” name
      • Date of creation
      • Brief description of the content
      • File type and other relevant features
      • Reference to the test script.
    • Information on the defects and the changes
    • Transfer and version documentation.
• 2. Other test (project) documentation - During the test process, various documents are received or created that are not meant for reuse, such as:
  • Project plans
  • Reports of the discussions (with lists of decisions and activities)
  • Correspondence, both on paper and electronic (e-mail)
  • Memos
  • (Project) standards and guidelines
  • Test, review and audit reports
  • Reports on progress and quality
  • Etc.

By means of a brief description, the content and the aim of the various products or documents are indicated. Besides listing the products to be delivered, norms and standards can also be supplied and reference made to templates.

Products

A description of the test products to be delivered including norms and standards and any reference to templates, established in the test plan.

Tools

Testware management tool.